<div id="table-of-contents">
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
<li><a href="#sec-1">1. About</a>
<ul>
<li><a href="#sec-1-1">1.1. Roadmap</a>
<ul>
<li><a href="#sec-1-1-1">1.1.1. <span class="todo TODO">TODO</span> Try using org files for the README</a></li>
<li><a href="#sec-1-1-2">1.1.2. <span class="todo TODO">TODO</span> HTTP Request and print YAML</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#sec-2">2. Meta About</a></li>
<li><a href="#sec-3">3. License</a></li>
<li><a href="#sec-4">4. Use</a></li>
</ul>
</div>
</div>

# About<a id="sec-1" name="sec-1"></a>

Project for code examples, snippets, language comparisons.

## Roadmap<a id="sec-1-1" name="sec-1-1"></a>

### TODO Try using org files for the README<a id="sec-1-1-1" name="sec-1-1-1"></a>

### TODO HTTP Request and print YAML<a id="sec-1-1-2" name="sec-1-1-2"></a>

Write some code that sends a request to some end point, receives json, and prints it out as yaml. Handle errors gracefully, at least by catching the stacktraces.
-   Perl5
-   Python3
-   Rust
-   Go
-   Haskell
-   etc

# Meta About<a id="sec-2" name="sec-2"></a>

Someone wrote me in orgmode.

# License<a id="sec-3" name="sec-3"></a>

Copyright 2019 vaeringjar.
Distributed dually under the CC BY-SA 4.0 and GPLv3+.

# Use<a id="sec-4" name="sec-4"></a>

Make edits with a plain text editor in README.org. Then open in emacs with org-mode and then do:

M-x org-md-export-to-markdown
